-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addition of release process doc #17680
Conversation
capture the current state of things
To echo Martin's comment, and given our today's discussion (the one in the UI/UX channel thread) I think it would make sense to postpone this until we can have a larger meeting, with EU/AU folks present, where we can discuss in more detail the release life cycle, formal testing of releases, and any related issues. That said, this document should absolutely be part of our documentation, I'm sure it'll be most helpful for the community. |
It might be beneficial to clarify the security commitment wrt what has been added here and also the release versioning. e.g. the following seems confusing now: Lines 13 to 20 in 8adfb7e
|
As mentioned in the doc, this just outlines the release cycle to set expectations.
This is nothing new in terms of policy, it's just trying to document the current state of things.
Please feel free to directly push any edits/additions/etc.
How to test the changes?
(Select all options that apply)
License